Auto Gain Adjusting Trailer Brake Controller

ABSTRACT

In various example embodiments, a system and method for determining a trailer brake gain signal for trailer brakes on a trailer being towed by a vehicle, and applying brakes to the trailer is disclosed. A method includes: providing predetermined calibration settings relating motor drive force to motor speed for a vehicle travelling at various speeds and providing accelerometer data. The method then determines that one or more vehicle performance parameters fall within threshold ranges and then determines both the vehicle weight and the trailer weight. The brake gain signal is determined based on the ratio of the current trailer weight and the original trailer weight. The brake gain signal is then transmitted to a trailer brake controller that applies trailer brakes according to the brake gain signal.

BACKGROUND Field of the Invention

This invention generally relates to transportation and more particularly relates to vehicles towing trailers and applying power to trailer brakes.

Background of the Invention

The proper control of trailers being hauled by a vehicle assures that the trailer can be towed in a safe manner. Trailer control includes proper attachment of the trailer to the tow vehicle, along with enough vehicle power to accelerate and bring the vehicle and trailer up to highway speeds. As important as the acceleration and towing capacity of the tow vehicle is the braking power and braking system to slow or stop the vehicle and trailer.

In many cases, the brakes of the vehicle are not adequate to bring the added load of the trailer to a stop safely. In these cases, brakes on the trailer itself assist in braking the trailer and its associated load. With brakes on the trailer assisting the brakes of the vehicle, the combined braking power assures that the vehicle and trailer can be stopped safely. Trailer brakes are typically controlled in tandem with the vehicle's braking system by sending an electrical gain signal from a brake controller to the trailer braking system. The gain signal communicates how much force to apply to the trailer brakes to the brake controller so that the proper amount of braking is delivered to the braking system.

Trailer brake controllers help the driver control vehicle and trailer combinations by applying the correct level of braking at the trailer, to help bring the combination to a stop. If too little braking is applied at the trailer, the vehicle brakes can be overloaded as the trailer pushes the vehicle along. If too much braking is applied at the trailer, the trailer may lockup the wheels, while the vehicle still has plenty of braking capacity.

Current trailer brake controllers monitor deceleration of the vehicle, and multiply the value by a gain to set the command signal to the trailer brakes. The driver manually sets the gain, via buttons or a knob. Setting the correct gain is critical for good operation, but drivers often get it wrong.

For smaller loads, it may not be that critical if the manual gain signal is not set correctly. However, as the load increases it becomes more important that the correct gain signal is communicated to the trailer brake controller.

SUMMARY

This invention has been developed in response to the present state of the art and, in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available systems and methods. Features and advantages of different embodiments of the invention will become more fully apparent from the following description and appended claims, or may be learned by practice of the invention as set forth hereinafter.

Consistent with the foregoing, a system and method for an auto gain adjusting trailer brake controller is disclosed. In order to determine how much braking force is required for the trailer being towed, a brake gain signal must be determined and transmitted to a brake controller. This gain signal is determined by first looking at preset values set up for the trailer brakes. These settings can be done at the time of the manufacturing of the trailer and the trailer brake control system. Secondly, user input can be included in the determination of a gain setting for the trailer brake controller. This is done by the user adjusting the gain by turning a knob or pushing buttons on an interface device or control panel either on the vehicle dash or on a control device connected to the brake controller.

the total weight of a vehicle, the drive force and speed of the vehicle comprising velocity and acceleration must be known in order to do the required calculations.

The gain is directly related to the weight of the trailer. Once the weight of the vehicle is known, then the weight of the trailer can be calculated and the gain can be adjusted. The first gain may be done manually, then weight sensing could modify the gain from there.

In order to determine vehicle weight, a force calculation may be made. When mass is known, the drive force may be calculated from the accelerometer and torque converter data. The device could take the driver through a calibration procedure. This would monitor drive force from the torque converter (low speed, 1st gear), dynamic load from accelerometer and mass (F=ma), to calculate the trailer brake force. The controller would sweep the trailer brake signal from low to high, and measure the brake force. This characteristic curve becomes the core of a braking strategy that may be used for that trailer. When the weight changes, the strategy can then adjust the gain such that the proper braking force is used.

To calculate the drive force of the electric powertrain, the motor current, voltage, and motor speed, must be known to determine the torque. This torque may be used to calculate a drive force. Drive force and longitudinal acceleration may be used to calculate mass. In hybrid powertrains, such as the powersplit IVT, or eCVT (Prius, Fusion), the motor torques may be used to sense the engine torque, such that the total torque delivered by the electric powertrain may be calculated. This total torque of all contributing electric motor components may then be used together with the torques from other power delivery system components including internal combustion engine drive forces to determine a total combined drive force. Drive force is the portion of the force generated by the drive wheels that accelerates the mass of a vehicle. Any friction, air drag, etc. present is not part of the drive force. During calibration, the system calculates this force by measuring the mass of the vehicle, and the acceleration. These values are then used to determine force F=m*a.

For hybrid vehicles, there are many drive forces that are combined to deliver a combined drive force. These comprise both positive and negative drive forces. Positive drive forces include internal combustion engines, electric motors, and other mechanical forces that contribute to the motive force driving the vehicle in the desired direction of travel. Negative drive forces comprise forces that diminish the motive force driving the vehicle in the desired direction. For example, brakes are negative drive forces when they are applied to slow the speed of the vehicle. Electric motors can be used to slow down or brake the speed of a vehicle when operating as generators or alternators to charge the batteries or energy storage devices. While acting as generators, electric motors are contributing a negative drive force. The combined drive force is the force delivered to the drive wheels that accelerates the mass of a vehicle.

In addition to drive forces, predetermined calibration settings relating force to motor or engine speed for a vehicle travelling at various speeds is also required. Accelerometer data may be altered based on filtered vehicle pitch and roll data, determining that one or more vehicle performance parameters fall within a threshold range, storing a plurality of data pairs that include longitudinal acceleration and drive force, and determining a slope of a line that linearly approximates the plurality of data pairs, the slope indicating a total weight, the total weight comprising a weight of the vehicle and a weight being hauled by the vehicle; the trailer brake gain signal is determined by multiplying the longitudinal acceleration by the original trailer gain and by the current trailer weight. This value is divided by the original trailer weight. This gain signal is sent to the brake controller that then applies trailer brakes according to the calculated gain signal.

In certain embodiments, the method includes providing predetermined calibration settings relating drive force to motor speed for a vehicle travelling at various speeds, providing accelerometer data to determine vehicle velocity, acceleration and direction of travel. The method may use of one or more processors, to determine that one or more vehicle performance parameters fall within threshold ranges which enables the determination of a vehicle weight. An initial gain setting is provided as a factory reset or as a user input via an adjustable knob or push buttons on a brake controller interface device. This gain setting is modified according to the trailer weight. The method further uses the trailer weight to determine a new gain signal based on the calculated trailer weight, which is then transmitted to a trailer brake controller, which applies brakes to the trailer according to the new gain signal.

In another embodiment, the determining a vehicle weight further includes: storing, in response to the vehicle performance parameters being within the threshold ranges, a plurality of data pairs, each data pair comprising a longitudinal acceleration and a drive force, the drive force determined according to a calibrated polynomial for a current velocity of the vehicle; determining a slope of a line that linearly approximates the plurality of data pairs, the slope indicating a total weight, the total weight comprising a weight of the vehicle and a trailer weight; determining the trailer weight by subtracting the weight of the vehicle; wherein the determining the slope of the line comprises: setting the initial y intercept of force vs. acceleration to zero; and performing regression analysis on the plurality of data pairs resulting in a first order drive force polynomial, a first order coefficient representing the total weight.

In one embodiment, the drive force comprises a combined drive force of all motor drive forces, engine drive forces and motive force devices; and wherein providing predetermined calibration settings further consists of relating motor drive force to motor speed for the vehicle traveling at various speeds.

In an embodiment, the vehicle performance parameters are selected from the group consisting of lateral acceleration, velocity, electric motor speed, electric motor operating in braking mode as a generator, engine speed, longitudinal acceleration, brakes not being applied, and a transmission gear ratio.

In another embodiment, the gain signal is adjusted based on the ratio of the current trailer weight divided by the original trailer weight.

In certain embodiments, the method includes retrieving one or more of the vehicle performance parameters from a computing device for the vehicle.

In an embodiment, the combined drive force is determined by determining a polynomial for each integer velocity of the vehicle by performing regression analysis on calibration data pairs for each integer velocity of the vehicle, the calibration data pairs comprising a calibration drive force, an electric motor speed and an engine speed, the calibration drive force determined by multiplying the weight of the vehicle with a longitudinal acceleration of the vehicle when the data pair was recorded.

The motor is a motive force device comprising one or more electric motors, internal combustion engines, and external combustion engine

In another embodiment the system includes a vehicle comprising one or more motors; one or more accelerometers that sense acceleration of the system; one or more processors; a drive force module that determines a combined drive force of one or more electric motors, engines and motive force devices; an interface module that retrieves one or more vehicle performance parameters; a performance module that determines whether the vehicle performance parameters fall within respective threshold ranges; a data module that stores, in response to the vehicle performance parameters being within the respective threshold ranges, a plurality of data pairs, each data pair comprising the longitudinal acceleration of the vehicle and a drive force for the vehicle, the drive force determined according to a calibrated polynomial for a current velocity of the vehicle; a weight module that determines the weight being hauled by the vehicle; a brake gain module the determines the brake gain based on current trailer weight and original trailer weight; a brake signal module that transmits a brake gain signal to a brake control module; and the brake control module that applies trailer brakes.

In a certain embodiment, a detection module records and compares the combined drive force RPM to vehicle speed, and uses this ratio to determine the vehicle's axle ratio and tire size, which is then used to correct the calculated mass.

In an embodiment, the vehicle performance parameters are selected from the group consisting of lateral acceleration, velocity, engine speed, longitudinal acceleration, brakes application status, and a selected transmission gear.

In another embodiment, the system includes the following reset functions: complete system reset upon vehicle being turned off; complete system reset upon vehicle pitch and shaking detection indicating load shift; and complete system reset upon vehicle travelling in reverse direction.

The system also includes in an embodiment, a calibration module that determines a polynomial for each integer velocity of the vehicle by performing regression analysis on calibration data pairs for each integer velocity of the vehicle, the calibration data pairs comprising a calibration drive force and an engine speed, the calibration drive force determined by multiplying the weight of the vehicle with a longitudinal acceleration of the vehicle when the data pair was received, the longitudinal acceleration including the force of gravity, the data module determining the drive force using the polynomial for a current speed of the vehicle.

In an embodiment, a computer readable storage medium storing executable instructions thereon, which, when executed by a processor, cause the processor to perform operations including: retrieving one or more performance parameters for a vehicle by one of communicating with diagnostic port for the vehicle and communicating with one or more accelerometers providing accelerometer data; determining a combined drive force; determining filtered data based on the vehicle pitch, roll or both; altering the accelerometer data based on the filtered data; determining that one or more vehicle performance parameters fall within a threshold range; storing, in response to the vehicle parameters being within the respective threshold ranges, a plurality of data pairs, each data pair comprising a longitudinal acceleration and a drive force, the drive force determined according to a calibrated polynomial for a current velocity of the vehicle; determining a slope of a line that linearly approximates the plurality of data pairs, the slope indicating a total weight, the total weight consisting of a weight of the vehicle and a weight being hauled by the vehicle; determining a brake gain signal according to the ratio of the current trailer weight to the original trailer weight; transmitting the brake gain to a trailer brake controller; and applying trailer brakes according to the gain signal. In a certain embodiment, the computer readable storage medium of claim also includes system reset functions: complete system reset upon vehicle being turned off; complete system reset upon vehicle pitch and shaking detection indicating load shift; and complete system reset upon vehicle travelling in reverse direction.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered limiting of its scope, the invention will be described and explained with additional specificity and detail through use of the accompanying drawings, in which:

FIG. 1 is an illustration depicting one scenario for use of a trailer brake controller 150, according to some example embodiments.

FIG. 2 is an illustration depicting another scenario according to one example embodiment.

FIG. 3 is an illustration depicting one example scenario for use of a trailer brake controller 150, according to one example embodiment.

FIG. 4 is an illustration depicting a trailer's rear wheel and axle assembly according to one example embodiment.

FIG. 5 is a schematic block diagram illustrating one embodiment of a trailer brake controller according to one example embodiment.

FIG. 6 is a schematic block diagram illustrating another embodiment of a trailer brake controller according to an example embodiment.

FIG. 7 is a flow diagram illustrating one example embodiment of a method for determining total weight, according to one example embodiment.

FIG. 8 is a flow diagram illustrating another example embodiment of a method for determining total weight, according to one example embodiment.

FIG. 9 is a flow diagram illustrating one example embodiment of another method for determining total weight, according to one example embodiment.

FIG. 10 is a flow diagram illustrating one example embodiment of a method for generating calibration polynomials that determine total weight, according to one example embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.

In various embodiments, a system as described herein determines a weight being hauled by a vehicle based many data points that include a measured longitudinal acceleration and a drive force, wherein the drive force is determined according to a calibrated polynomial for a current velocity of the vehicle.

Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive and/or mutually inclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, advantages, and characteristics of the embodiments may be combined in any suitable manner. One skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.

These features and advantages of the embodiments will become more fully apparent from the following description and appended claims, or may be learned by the practice of embodiments as set forth hereinafter. As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, and/or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having program code embodied thereon.

Many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence.

For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in software for execution by various types of processors. An identified module of program code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the program code may be stored and/or propagated on in one or more computer readable medium(s).

The computer readable medium may be a tangible computer readable storage medium storing the program code. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

More specific examples of the computer readable storage medium may include but are not limited to a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, and/or store program code for use by and/or in connection with an instruction execution system, apparatus, or device. Computer readable storage medium excludes computer readable signal medium and signals per se.

The computer readable medium may also be a computer readable signal medium. A computer readable signal medium may include a propagated data signal with program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electrical, electro-magnetic, magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport program code for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including but not limited to wire-line, optical fiber, Radio Frequency (RF), or the like, or any suitable combination of the foregoing.

In one embodiment, the computer readable medium may comprise a combination of one or more computer readable storage mediums and one or more computer readable signal mediums. For example, program code may be both propagated as an electro-magnetic signal through a fiber optic cable for execution by a processor and stored on RAM storage device for execution by the processor.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, PHP or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The computer program product may be shared, simultaneously serving multiple customers in a flexible, automated fashion. The computer program product may be standardized, requiring little customization and scalable, providing capacity on demand in a pay-as-you-go model. The computer program product may be stored on a shared file system accessible from one or more servers.

The computer program product may be integrated into a client, server and network environment by providing for the computer program product to coexist with applications, operating systems and network operating systems software and then installing the computer program product on the clients and servers in the environment where the computer program product will function.

In one embodiment software is identified on the clients and servers including the network operating system where the computer program product will be deployed that are required by the computer program product or that work in conjunction with the computer program product. This includes the network operating system that is software that enhances a basic operating system by adding networking features.

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the invention. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by program code. The program code may be provided to a processor of a general purpose computer, special purpose computer, sequencer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The program code may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The program code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the program code which executed on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the program code for implementing the specified logical function(s).

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures. Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and program code.

FIG. 1 is an illustration depicting one scenario for use of a trailer brake controller 150, according to some example embodiments. In one embodiment, the trailer brake controller determines vehicle performance conditions that increase accuracy of total weight determination as described herein. Certain performance parameters include, but are not limited to, lateral acceleration, engine speed, longitudinal acceleration, transmission gear selection, application of brakes, operation of energy recovery systems, operation of special or unique operation modes, or other, or the like.

As will be further described herein, determination of lateral acceleration using the Earth as a point of reference allows such a trailer brake controller to account for the force of gravity in various drive force calculations. Accordingly, the trailer brake controller 150 performs accurately in a wide variety of slopes and varying terrain.

In order to accurately determine the system weight, the pitch of the vehicle must be determined. Vehicle pitch is monitored when the vehicle comes to a stop. This pitch is then compared to the pitch when the vehicle starts accelerating forward. The difference of these two pitches (pitch at rest vs. pitch upon forward motion) due to a load in the bed of the vehicle, must be corrected to adjust the accelerometers for this bias.

When the vehicle is turning, the data must be filtered out. Turn events are sensed through the lateral accelerometers. However, many roads have a crown, so the vehicle may actually be travelling in a straight line. In this case, the lateral accelerometer will show a value, filtering out what should be good data. Roll compensation solves this problem. The lateral accelerometer is zeroed out right before the vehicle takes off, and filters only for changes to that accelerometer. A steering wheel sensor or gyro may also sense turning events.

The accelerometers determine their orientation in a vehicle a few seconds after the diagnostic connector is plugged in. Many users may have modified the suspension of their vehicle so that the pitch is no longer the same as at the factory. By re-orienting during install, a custom accelerometer setting for each vehicle is established, determining longitudinal, lateral and vertical axes no matter what the orientation of the vehicle.

Reset logic provides for all settings to be reset to zero and the system to be restarted upon the occurrence of any one or more of the following: complete system reset upon vehicle engine being turned off; complete system reset upon vehicle pitch and shaking detection indicating load shift; and complete system reset upon vehicle travelling in reverse direction.

Since a vehicle may have been modified after the factory, axle and tire size detection is also calculated in one embodiment of the invention. Axle ratio and tire size detection is determined when the vehicle is travelling at a speed of between 60 mph to 80 mph, and O_(g−) (−0.2 g), Engine RPM/vehicle speed is recorded. This ratio enables the algorithm to learn the vehicle's axle ratio and tire size. Once recorded, it is used to correct the mass calculated from the algorithm.

After determining that the vehicle is operating within certain performance thresholds, the trailer brake controller 150 stores performance data pairs including, longitudinal acceleration and a drive force. As will be further described herein, the drive force may be determined based on calibration polynomials generated by the trailer brake controller 150.

The trailer brake controller 150 then determines the slope of a line that approximates the data pairs wherein the slope of the line indicates a total weight. The trailer brake controller 150 then subtracts a known weight of the vehicle to determine the total weight of the vehicle. Of course, one skilled in the art may recognize other ways to determine the slope of a line that approximates a set of data points and this disclosure is meant to include all such ways. Accordingly, the trailer brake controller 150 determines a total vehicle weight based, at least in part, on learned drive force behavior of the vehicle and current drive force compared with longitudinal acceleration.

The trailer brake controller 150 may then display the determined total weight to a driver of the vehicle. This allows the driver to adjust operation of the vehicle based on knowledge of the total weight. For example, in response to total weight that is 90% of the vehicle's haul capacity, the user may understand to apply braking earlier or more aggressively. In another example, the user may drive more slowly, or adjust other operation of the vehicle in order to maintain safe operating conditions.

In another embodiment, the trailer brake controller 150 actively adjusts operation of the vehicle without user intervention. For example, the trailer brake controller 150 may, in response to total weight exceeding a threshold value, increase the brake gain signal to a trailer brake controller.

Therefore, the operation of the vehicle, from the user's frame of reference may not be significantly different than operation of the vehicle while hauling significant weight. Furthermore, as will be described, the trailer brake controller 150 adjusts systems that control operation of the vehicle based on the determined total weight. Thus various systems that control operation of the vehicle may be configured to perform with consideration of the actual total weight.

A vehicle hauling a weight as described herein may include a vehicle carrying or towing another weight. In one example, a vehicle hauling a load may include a truck towing one or more trailers. In another example, a vehicle hauling a load may include a truck carrying goods or other items in a bed of the truck. In another example, a vehicle hauling a load may include an automobile with significant weight beyond passengers where the weight may alter the performance characteristics of the vehicle. Of course, one skilled in the art may appreciate a wide variety of other vehicles carrying or towing trailers, goods, items, other vehicles, recreational vehicles, motorcycles, all-terrain vehicles, cargo, other items, or the like.

In one embodiment, determining a weight of goods or items being carried or hauled helps ensure that the vehicle operates within one or more safety parameters. In one example, the trailer brake controller 150 determines if the weight being hauled exceeds a safety threshold. In one example, a manufacturer for the vehicle may have specified a maximum tow capacity.

In another embodiment, the trailer brake controller 150 has a knob 110 that can be turned to adjust the gain for the trailer brake controller 150. Another embodiment comprises a gain adjustment knob 120 mounted on the dash with electrical wiring 130 connecting it to the trailer brake controller 150.

As indicated in FIG. 1, the trailer brake controller 150 may be implemented as a physical hardware module that plugs into a diagnostic port for the vehicle. Thus the trailer brake controller 150 communicates with a computer for the vehicle to determine various vehicle performance properties, such as, but not limited to, engine speed, throttle position, a transmission gear selection, special and/or unique operating modes, or the like, as described herein. In certain embodiments, the trailer brake controller 150 may be purchased by a user and installed in any vehicle with a capable communication port. Thus, the trailer brake controller 150 may be installed in a vehicle after purchase of the vehicle and does not need to be installed by a manufacturer of the vehicle.

FIG. 2 is an illustration depicting another scenario according to one example embodiment. According to this example embodiment, the trailer brake controller 150 may transmit the determined total weight to a display 202. Information regarding the braking system, both the vehicle brakes and trailer brakes may also be displayed on the dashboard instrument panel 204 via an OEM implementation, or on the digital readout display 208 of the vehicle's car radio 206. A driver of the vehicle may view the display and operate the vehicle according to the displayed total weight, or perform other appropriate actions having knowledge of the weight being hauled by the vehicle. In other example embodiments, the display 202 is configured to display messages, alerts, adjustments, warnings, or other indications to a user.

FIG. 3 is an illustration depicting one example scenario for use of a trailer brake controller 150, according to one example embodiment. In this example embodiment, the vehicle is a truck 302, and the weight being hauled is a trailer 304.

The amount of weight included in the trailer 304 may vary widely based on an amount of equipment being stored in the trailer 304. Therefore, a driver of the vehicle may or may not realize the haul weight of the trailer 304. This presents a danger to the driver of the vehicle. Therefore, the trailer brake controller 150, according to one embodiment, assists a user to safely operate a vehicle that is hauling a weight.

In this example embodiment, the trailer brake controller 150 communicates with the vehicle control system via a wireless connection 306. In one example, the trailer brake controller 150 may be communicating using Bluetooth™, near field communications (NFC), or any other wireless communication protocol as one skilled in the art may appreciate. In another embodiment, the trailer brake controller 150 is connected to the trailer braking system via the wiring 310 to a vehicle mounted connector 325, which is connected to the trailer connector 326. Wiring 330 extends from the connector 326 to the brake controller 315. The trailer brake control interface 315 receives the gain signal and applies the trailer brakes 320 according to the gain signal.

FIG. 4 is an illustration depicting another example according to one example embodiment. A trailer's rear wheel and axle assembly 450 is shown. Trailer brakes 320 are controlled by trailer brake control interface 315 which receives the gain signal from the brake controller.

FIG. 5 is a schematic block diagram illustrating one embodiment of a trailer brake controller 150, according to one example embodiment. In this example embodiment, the trailer brake controller 150 includes processors 102, memory 104, a drive force module 106, a vehicle pitch and roll module 108, one or more accelerometers 210, a performance module 240, an interface module 220, a data module 250, a weight module 230, a brake gain module 260, and a brake signal module 280 and a brake control module 290.

Processors 102 include any and/or all processors capable of executing executable code as described herein. The memory 104 includes the various computer-readable storage mediums described herein. According to one example embodiment, the memory 104 stores executable code for causing the processor 102 to perform various functions and/or methods as described herein regarding the modules (e.g. the performance module 240, the interface module 220, the data module 250, the weight module 230, the brake gain module 260, brake signal module 280 and brake control module 290).

In one example embodiment, the one or more accelerometers 210 includes a triaxial accelerometer. As described herein, and as one skilled in the art may appreciate, the triaxial accelerometer senses acceleration, at a single-point, in three planes. Each of the three planes may be perpendicular to another of the three planes. According to a Cartesian coordinate system, the three planes are represented by X, Y, and Z planes as one skilled in the art may appreciate. In one embodiment, the triaxial accelerometer measures acceleration and transmits the acceleration in any and/or all of the planes to the interface module 220. The triaxial accelerometer also includes the force of gravity in the acceleration values.

In another embodiment, the accelerometers 210 include three distinct accelerometers configured to sense acceleration along different axis. Of course, one skilled in the art may recognize other ways to detect acceleration in three different planes and this disclosure is meant to include all such ways. Furthermore, the triaxial accelerometer may not be limited regarding frequency range, amplitude range, resonance, sensitivity, temperature range, shock range, or the like as one skilled in the art may appreciate.

The accelerometer(s) 210 therefore, determine an acceleration of the trailer brake controller 150 including the force of gravity. Therefore, based on measurements by the accelerometer(s) 210, the trailer brake controller 150 also determines an orientation of the trailer brake controller 150. Accordingly, the trailer brake controller 150 may determine whether the vehicle is traveling up a hill, down a hill, or is driving along an incline.

In one embodiment, the interface module 220 is configured to retrieve one or more values. In one example, the interface module 220 receives an initial weight for a vehicle not including any hauled weight from a user interface. For example, the interface module 220 receives a manufacturer value for the vehicle weight from a user, manufacturer, or 3rd party source of the vehicle.

In another example embodiment, the interface module 220 retrieves one or more values via a communication port for the vehicle. For example, the interface module 220 may communicate with a computer for the vehicle via an On-Board-Diagnostics (OBD) interface, and ODB-II interface, or other, or the like. In another embodiment, the interface module 220 may receive vehicle velocity, engine speed, or other vehicle performance parameters, or the like via the diagnostic port.

In one example embodiment, the trailer brake controller 150 requests vehicle velocity and engine RPM's from a vehicles computing device to determine calibration polynomials and subsequently determine total weight. Accordingly, the interface module 220 does not need other variables from a computing device for the vehicle. [0070] In one embodiment, the interface module 220 retrieves one or more acceleration values from one or more accelerometers 210. The interface module 220 may differentiate between lateral acceleration, longitudinal acceleration, and vertical acceleration based, at least in part on measurements from the accelerometers 210. Therefore, in certain embodiments, the interface module 220 may determine longitudinal acceleration using one or more accelerometers.

In another embodiment, the interface module 220 determines engine speed by alternator noise on a power line of the vehicle. In one embodiment, the interface module 220 determines vehicle velocity and/or acceleration from a GPS device, or other location device as one skilled in the art may appreciate. In one embodiment, the interface module 220 includes an orientation sensor. For example, the interface module 220 may sense orientation in order to determine acceleration values, such as, but not limited to, lateral acceleration, longitudinal acceleration, or the like. Therefore, in certain embodiments, the interface module 220 may determine acceleration values regardless of an orientation of the trailer brake controller 150.

In another embodiment, the interface module 220 includes one or more buttons to receive commands from a user. For example, the interface module 220 may include a button for a user to press that may indicate a calibration procedure is to be initiated. In response to the interface module 220 detecting a press of the button, the data module 250 initiates a calibration procedure as will be further described.

In certain embodiments, the performance module 240 determines whether a vehicles performance falls within a set of threshold ranges. In some examples, the trailer brake controller 150 determines whether lateral acceleration, engine speed, longitudinal acceleration, transmission gears, and other performance parameters are within respective threshold ranges.

In certain embodiments, the drive force module 106 determines the total of all drive forces including electric motors, internal combustion engines and all other devices providing positive force to move the vehicle in the desired direction, typically forward motion. In other embodiments, the drive force module includes all positive and negative drive forces including brakes or other devices that inhibit the positive force which normally moves the vehicle in the desired direction.

In other embodiments, the vehicle pitch and roll module 108 determines the pitch and roll of the vehicle based on accelerometer data along with data provided by the on-board computer and on board processors. In another embodiment, pitch and roll data comes from wireless data provided from accelerometers in personal electronic devices.

For example, the performance module 240 determines whether lateral acceleration falls between −0.05 standard gravity units and +0.05 standard gravity units. In response

to the lateral acceleration being within the threshold range, the data module 250 records one or more data pairs including drive force and longitudinal acceleration.

In another example, performance module 240 determines whether engine speed for the vehicle is within a threshold range. For example, a combustion engine operates more or less efficiently at different engine speeds, therefore, the trailer brake controller 150 may determine a weight being hauled by the vehicle in response to the combustion engine operating within a threshold range of revolutions per minute (RPM's). For example, the performance module 240 determines that in response to the engine operating at between 900 RPM's and 3000 RPM's, the data module 250 may collect one or more data points.

In another example, the performance module 240 determines whether an engaged drivetrain gear differs from a drivetrain gear engaged while the calibration module generated one or more calibration polynomials as described herein.

In another example, exterior forces that effect performance of a vehicle are less at lower velocities. Examples includes, air resistance, oil resistance, wheel bearing resistance, internal drag forces, such as, but not limited to, friction, wear, powertrain friction or drag. These other forces may or may not act along the longitudinal axis of the vehicle. Therefore, in order to increase accuracy of weight determinations, the performance module 240 may also wait for the vehicle's velocity to be within a threshold range before the data module 250 records one or more data pairs. In one example, the performance module 240 determines whether the vehicle is moving between 2 and 20 kilometers per hour (KPH).

In another example, a vehicle that is accelerating is not typically applying brakes or other forces, therefore, performance module 240 may also ensure that the vehicle is accelerating before the data module 250 stores data pairs. In one example, the performance module 240 determines that a longitudinal acceleration for the vehicle is between 0.05 standard gravity units and 1 standard gravity units. In response, the data module 250 stores one or more data pairs as described herein.

In another example embodiment, the performance module 240 determines whether the vehicle's engine is operating in any special or unique modes. For example, in response to determining that the vehicle's engine is operating in a decreased capacity (e.g. a fuel efficiency mode), the data module 250 may not store data pairs. Special or unique modes includes, but is not limited to, use of hybrid systems, electric drive assistance, power recovery modes, fuel efficiency modes, partial engine usage, or other non-conventional or reduced power engine operation modes.

In one example embodiment, in response to the performance module 240 determining that one or more vehicle performance parameters are within respective threshold ranges, the data module 250 stores data pairs representing a current operating state for the vehicle. The data pairs include drive force and longitudinal acceleration. [0080] In another embodiment, the interface module 220 may divide the acceleration into multiple components (e.g. 3 components). For example, the performance module 240 may determine that a portion of the acceleration may be lateral acceleration, a portion for longitudinal acceleration and another portion for vertical acceleration. Lateral acceleration may be associated with a change in lateral movement not associated with force from the engine. Therefore, in certain embodiments, the performance module 240 may determine a portion of the total acceleration associated with applied engine force (longitudinal acceleration). This longitudinal acceleration may include acceleration along or parallel with the axis vehicle movement. Lateral acceleration may be perpendicular to the longitudinal axis of the vehicle.

The data module 250 stores data pairs representing the current performance of the vehicle. The data pairs include a drive force and a longitudinal acceleration. In one embodiment, the data module 250 may generalize drive forces (F_(Drive)) by generally combining drag forces (F_(Drag)) and acceleration (F_(Accel)) forces using the following equation (Equation 1):

F _(Drive) =F _(Drag) +F _(Accel)

In another embodiment, a vehicle may include a transmission with a torque converter. A torque converter, in certain embodiments, may decouple the transmission and the engine of the vehicle. This may allow the vehicle to stop moving although the engine for the vehicle may continue operating. A torque converter may also include an impeller (i.e. a pump) that may be attached to the engine, and a turbine that may be attached to a transmission for the vehicle. In one example, hydraulic fluid may be pumped from the impeller to the turbine. The increased hydraulic pressure from the impeller may cause the turbine to spin at a similar speed which may increase torque transmitted to the transmission.

Therefore, where engine speed is represented as S_(E), and Vehicle velocity is represented as S_(V), turbine torque (T_(T)) may be represented as a function of engine speed and vehicle velocity as follows (Equation 2):

T _(T) =f(S _(E) ,S _(V))

In one embodiment, a transmission ratio may directly relate turbine torque to drive force. Furthermore, turbine torque may be represented by a function of engine speed and vehicle velocity. For example (Equation 3):

F _(Drive) =f(T _(T))

Combining equations 2 and 3 allows drive force to be represented as a function of engine speed and vehicle velocity (Equation 4):

F _(Drive) =f(S _(E) ,S _(V))

Solving equation 1 for the force of acceleration results in (Equation 5):

F _(Accel) =F _(Drive) −F _(Drag)

Drag force (F_(Drag)) may be influenced by many factors. Any of these factors may vary with speed. In one example, air resistance may increase with vehicle velocity. In another example, internal friction may increase as components spin faster. Therefore, drag force may be written as a function of vehicle velocity resulting in (Equation 6):

F _(Drag) =f(S _(V))

In other embodiments, drive force may also be depicted as a function of engine speed and vehicle velocity. Therefore (Equation 7):

F _(Drive) −F _(Drag) =f(S _(E) ,S _(V))

Further noting that a force of acceleration is the mass (m) (e.g., weight) being accelerated multiplied by the acceleration (a) results in (Equation 8):

F _(Accel) =m·a

In one embodiment, longitudinal acceleration may be depicted as a_(lon) the force of acceleration may be calculated as follows (Equation 11):

F _(Accel) =C ₂ ·a _(lon) +C ₁

The calibration module 270 may perform regression analysis on the resulting data pairs and the haul weight may be C₂ minus the calibration weight (the weight of the vehicle performing the hauling). In response to the data module 250 storing 50 or more data pairs, and the regression error falling below 0.05, the output module 280 may display the haul weight. In one specific example, the calibration module 270 uses recursive least squares as one skilled in the art may appreciate. In other examples, the calibration module 270 generates a cubic or 4th order polynomial.

In order to initiate the regression analysis, the y intercept of the force vs. acceleration curve is set to zero. This allows for a reading to be taken with just one set of data points, even if they are clustered together.

In one embodiment, the weight may be determined using the following equation where n=the number of data pairs of drive force and longitudinal acceleration (equation 12):

$C_{2} = \frac{{n \cdot {\sum^{n}\left( {a_{lon} \cdot F_{Drive}} \right)}} - {\sum^{n}{\left( F_{Drive} \right) \cdot {\sum^{n}\left( a_{lon} \right)}}}}{{n \cdot {\sum^{n}\left( a_{lon}^{2} \right)}} - {\sum^{n}\left( a_{lon} \right)^{2}}}$

In one example embodiment, the weight module 230 is configured to determine the weight being hauled by the vehicle by determining a slope of a line that approximates the set of data pairs acquired by the data module 250. The weight module 230 may determine a line that approximates the data pairs in any way as one skilled in the art may appreciate. In one example, the weight module 230 applies a linear regression algorithm, or other, or the like. In another example embodiment, the weight module 230 applies the linear regression algorithm until the error falls below 0.05.

The weight module 230 then determines the slope of the line resulting from the linear regression algorithm. In this example embodiment, the slope of the line represents the total weight (including the weight of the vehicle and the weight being hauled by the vehicle). Therefore, the weight module 230 also determines the amount of weight being hauled by the vehicle by subtracting the known weight of the vehicle from the total weight.

In one embodiment, the brake gain module 260 alters vehicle operation based on the determined vehicle haul weight. In one example, the brake gain module 260 increases a gain for a braking system in response to determining that a determined haul weight falls within a range of threshold values. In one example, where the haul weight for a trailer exceeds 90% of the maximum haul weight for the vehicle, the brake gain module 260 increases brake gain for the trailer to a maximum value. The brake signal module 280 transmits the modified brake gain signal to the brake control module 290. The brake control module 290 causes the trailer braking system to deliver the force scaled according to the gain signal to the trailer brakes. In another example, modifying a gain for a braking system of the vehicle may accommodate increased haul weight for an automated collision detection system. Therefore, in response to an anticipated collision, the collision detection system may increase braking automatically based on the vehicle haul weight.

Typical trailer brake signal is calculated from: TrailerBrakeSignal=LongitudinalAccel*TrailerGain. According to the present embodiment, the gain signal is modified according to: TrailerBrakeSignal=LongitudinalAccel*TrailerGain*(Trailer weight current/Trailer weight original). Trailer weight original and current would come from the described weight sensing algorithm. The trailer brake controller comprises the invented logic integrated within. An integrated trailer brake controller is similar to the aftermarket version, but would be integrated into the vehicle, sharing some sensor inputs (such as accelerometer) with other vehicle systems.

FIG. 6 is a schematic block diagram illustrating another embodiment of a trailer brake controller 150, according to one example embodiment. In this example, the trailer brake controller 150 includes processors 102, memory 104, a drive force module 106, a vehicle pitch and roll module 108, one or more accelerometer(s) 210, the performance module 240, the interface module 220, the data module 250, the weight module 230, the brake gain module 260, a calibration module 270, a brake signal module 280, a brake control module 290 and an output module 295. The processor 102, the memory 104, the accelerometer(s) 210, the performance module 240, the interface module 220, the data module 250, the weight module 230, and the brake gain module 260, the brake signal module 280, the brake control module 290 and output module 295 may or may not be substantially similar modules depicted in FIG. 5.

In one embodiment, the trailer brake controller 150 includes an output module 280 that is configured to transmit the determined total weight to a remote system for display.

In certain embodiments, the drive force module 106 determines the total of all drive forces including electric motors, internal combustion engines and all other devices providing positive force to move the vehicle in the desired direction, typically forward motion. In other embodiments, the drive force module includes all positive and negative drive forces including brakes or other devices that inhibit the positive force which normally moves the vehicle in the desired direction.

In other embodiments, the vehicle pitch and roll module 108 determines the pitch and roll of the vehicle based on accelerometer data along with data provided by the on-board computer and on board processors. In another embodiment, pitch and roll data comes from wireless data provided from accelerometers in personal electronic devices.

In one embodiment, the output module 280 outputs one or more values for display to a user or driver of the vehicle. Informing a driver of a vehicle that is hauling a load may increase the user's ability to correctly estimate the performance capabilities of the vehicle. Accordingly, a user may be better informed and more appropriately react to real driving scenarios.

In another embodiment, the output module 280 may notify a user or driver of the vehicle in response to determining that the vehicle weight (including any load) exceeds a recommended maximum load weight. In one example, the output module 280 may transmit the determined load weight to a remote display via a wired or a wireless connection. For example, the output module 280 may transmit a value representing the load weight via low energy Bluetooth, or other transmission medium as one skilled in the art may appreciate.

In one embodiment, the output module 280 periodically updates a displayed load weight. For example, the output module 280 updates the load weight every 10 seconds, in response to a new weight being determined, or other interval.

In another example embodiment, the calibration module 270 generates a second order polynomial that approximates a calibration drive force and engine speed curve for each velocity of the vehicle. The data module 250 may use these polynomials to determine drive force as will be further described. The calibration module 270 may perform quadratic regression analysis on data pairs that include calibration drive force and engine speed.

As previously described, the performance module 240 determines whether vehicle performance parameters fall within respective threshold ranges. Therefore, the calibration module 270 may generate the polynomials in similar conditions as the weight module 230 determines a weight being hauled by the vehicle. In one specific example, the calibration module 270 delays generating the polynomials in response to the vehicle traveling up a hill, down a hill, or is at another incline.

In one embodiment, the interface module 220 receives the known weight of the vehicle and the force of acceleration may be measured by the one or more accelerometer(s) 210. The drive force minus the drag force may be solved as a function of engine speed and vehicle velocity. In other embodiments, this calibration method may not require the drag force to be estimated or learned.

In certain embodiments, the data module 250 stores data pairs that includes engine speed and a calibration drive force. Plotting multiple data points may reveal a quadratic trend in the relationship between engine speed and the drive force. The weight module 230 may perform regression analysis on the data points to determine coefficients of a quadratic polynomial that best fits the recorded data points. After the regression error decreases to an acceptable value, the weight module 230 stores the coefficient values for the best fit polynomial. In one example, the weight module 230 stores the coefficient values after the regression error falls below 0.05. Of course, other values may be used as one skilled in the art may appreciate.

Because the data pairs include engine speed and drive force, factors downstream of the engine are accounted for in the calibration polynomials. For example, because each velocity has a different associated polynomial, the polynomials for higher velocities naturally include drag effects due to air resistance, internal friction, and all other forces that effect acceleration of the vehicle are accounted for. In one example, larger tires increase drag and the calibration polynomials inherently include the increased drag. In another example, a modified final drive ratio, an updated or repaired torque converter or transmission, or other changes that affect an amount of drive force required to accelerate the vehicle are all accounted for in the calibration polynomials.

In another example embodiment, the calibration module 270 recalibrates (e.g. generates new polynomials, or updated polynomial coefficients) in response to any of these effects changing. For example, the calibration module 270 may instruct the user to request a recalibration in response to installing different sized tires on the vehicle. In other examples, the calibration module 270 instructs the user to request recalibration in response to any of the following: vehicle body modifications (e.g. a change that affect wind resistance), changing an oil weight, changing a final gear ratio, or other change that may affect an amount of drive force needed to accelerate the vehicle.

In one embodiment, the weight module 230 estimates the weight of the vehicle (with trailer, cargo, goods, etc.) by calculating the force of acceleration as a function of engine speed (S_(E)) as previously described. In one example, a quadratic equation may include a three coefficient values, CO, C1, and C2. The quadratic equation may take the form (Equation 9):

C ₂ ·S _(E) ² +C ₁·(S _(E))+C ₀

Therefore (Equation 10):

F _(Accel)(C ₂ ·S _(E) ² +C ₁ ·S _(E) +C ₀)=m·a

In one embodiment, the calibration module 270 may determine weight of the vehicle including hauled goods by plotting the force of acceleration (F_(Accel)) versus actual acceleration (a). The plot may indicate a linear trend. The calibration module 270 may perform regression analysis to find a coefficient representing a difference between the force of acceleration and weight multiplied by the acceleration plus the coefficient.

In another embodiment, the weight module 230 estimates the weight of the vehicle using the coefficients (C2, C1, Co) used to calculate the force of acceleration. In another embodiment, the weight module 230 may forget coefficient values, data points, or the like in response to being powered down. This may allow the calibration module 270 to determine new coefficient values each time the vehicle is power cycled. In another embodiment, the calibration module 270 provides a button for a user. In response to a user pressing the button, the calibration module 270 may erase current coefficient values and may determine new coefficient values. Therefore, in certain embodiments, the calibration module 270 determines new coefficient values each time a user changes a load weight, or the like, for the vehicle.

In one example, the performance module 240 determines if vehicle velocity falls between 2 and 20 miles per hour. In another example, the performance module 240 determines if engine speed is above an idle speed (e.g. 900 RPM's). In another example, the performance module 240 determines if a transmission for the vehicle is operating in a first gear. For example, the performance module 240 determines if a transmission for the vehicle is operating in a first gear based on a comparison between engine speed and vehicle velocity. In another example, the performance module 240 determines if the vehicle is currently experiencing low lateral acceleration as compared with longitudinal acceleration. For example, if lateral acceleration is 10% or less of the longitudinal acceleration. In another example, the calibration module 270 may determine if the vehicle pitch rate falls below a threshold value, such as, but not limited to 5%. In another example, the performance module 240 determines if an engine for the vehicle is currently operating within a temperature range. In a further embodiment, the performance module 240 determines if one or more of the foregoing conditions are met.

In response to determining if one or more inputs fall within threshold values, the calibration module 270 may multiply the acceleration by the user entered weight to calculate the drive force. The calibration module 270 may store the drive force in tables by velocity. Because the data module 250 stores the drive force due to the weight and the measured longitudinal acceleration, the data pairs inherently include other forces that affect the acceleration. Therefore, in one example, as wind resistance increases at higher velocities, the association between drive force and acceleration includes these forces without measuring the wind resistance at the higher velocities. For example, because the increased wind resistance ultimately affects the drive force I acceleration relationship, the calibration module 270 accommodates these and even other potentially unknown forces by separating the data pairs into separate table by velocity of the vehicle.

Furthermore, because the data pairs include drive force as determined based on the weight of the vehicle and measured acceleration, the drive force is a calculated drive force instead of a measured one. Therefore, the relationship indicated in the data pairs recorded by the data module 250 is based on drive force due to acceleration vs acceleration, which of course, differs from measured drive force vs acceleration. As one skilled in the art may appreciate, using a measured drive force in this stage of the calculations would not effectively include other forces that affect the acceleration of the vehicle.

Also, the drive force (due to acceleration) provides increased accuracy by determining the drive force in a first selectable gear and does require higher velocities to determine a weight being hauled by the vehicle.

The calibration module 270 may perform regression analysis on each table of data for a given velocity of the vehicle. The error may also be calculated for each data set according to the regression analysis. If the error does not fall below an error threshold value, the calibration module 270 may perform further regression analysis. In one embodiment, if the error does not fall below the error threshold value after a threshold amount of time, the calibration module 270 may delete the current coefficient values so that they are not used in weight estimation. If the error falls below the error threshold value, the calibration module 270 may store the resulting polynomial coefficients as previously described.

FIG. 7 is a flow diagram illustrating one example embodiment of a method 700 for determining total weight, according to one example embodiment. Operations in the method 700 may be performed by the trailer brake controller 150, using modules described above with respect to FIGS. 5 and 6. As shown in FIG. 7, the method 700 includes operations 710, 720, 730, 740, 750, 760 and 770.

In one embodiment, the method 700 begins and at operation 710, the performance module 240 determines that one or more vehicle performance parameters fall within respective threshold ranges. The method 700 continues at operation 720 and the data module 250 stores a plurality of data pairs. In another embodiment, the storing is in response to the vehicle parameters being within the respective threshold ranges. In another embodiment, each of the data pairs includes longitudinal acceleration and a drive force.

The method continues at operation 730 and the slope determination module determines a slope of a line that linearly approximates the plurality of data pairs. In one embodiment, the slope of the line represents a total weight that includes the weight of the vehicle and the weight being hauled by the vehicle. The method 700 continues at operation 740 and the weight module determines the trailer weight by subtracting the weight of the vehicle from the value representing the slope of the line in module 730. The method continues at operation 750 and the brake gain module determines the gain which is transmitted to the controller for brake control. The gain signal is transmitted at operation 760 to the trailer brake control interface, and the trailer brakes are applied at operation 770.

FIG. 8 is a flow diagram illustrating another example embodiment of a method for determining total weight, according to one example embodiment. Operations in the method 800 may be performed by the trailer brake controller 150, using modules described above with respect to FIGS. 5 and 6. As shown in FIG. 8, the method 800 includes operations 810, 820, 830, 840, 850, 860, and 870.

The method 800 begins and at operation 810 the interface module 220 retrieves one or more vehicle performance parameters as described in paragraph 72 through 79. In one example, the method 800 begins in response to an engine for the vehicle starting. The method 800 continues at operation 820 and the performance module 240 determines whether the vehicle performance parameters are within respective threshold ranges. In response to one of the vehicle performance parameters not being within a threshold range, the method 800 continues at operation 810.

In response to each of the vehicle performance parameters being within their respective threshold ranges, the method 800 continues at operation 830 and the data module 250 stores a data pair that includes longitudinal acceleration of the vehicle and a drive force for the vehicle.

In one embodiment, the data module 250 determines the drive force based on a calibration polynomial for each velocity of the vehicle as described in paragraphs 104-109. For example, the calibration module 270 may have generated a polynomial for the drive force line of the vehicle when traveling at 10 kilometers per hour (KPH). In response to the vehicle currently traveling at 10 KPH, the weight module 230 solves the polynomial for the drive force.

The method 800 continues at operation 840 and the data module 250 determines whether a threshold number of data pairs have been stored. In response to the number of data pairs being stored being below a threshold value, the method 800 continues at operation 810.

In response to the number of data pairs being stored exceeding the threshold value, the method 800 continues at operation 850 and the weight module 230 performs linear regression analysis on the data pairs. In response to the linear regression error not being below an error threshold value (e.g. 0.05), the method 800 continues at operation 850 and the weight module 230 continues the linear regression algorithm.

In response to the error being below the threshold error value, the method continues at operation 870 and the weight module 230 solves the polynomial resulting from the linear regression analysis for the total weight of the vehicle and the weight of the trailer. Operation 880 determines the brake gain.

FIG. 9 is a flow diagram illustrating one example embodiment of another method 900 for determining total weight, according to one example embodiment. Operations in the method 900 may be performed by the trailer brake controller 150, using modules described above with respect to FIGS. 5 and 6. As shown in FIG. 9, the method 900 includes operations 910, 920, 930, 940, 950, 960 and 970.

In one embodiment, the method 900 begins and at operation 910, the performance module 240 determines that one or more vehicle performance parameters fall within respective threshold ranges. The method 900 continues at operation 920 and the data module 250 stores a plurality of data pairs. The method 900 continues at operation 930 and the weight module 230 determines a slope of a line that linearly approximates the plurality of data pairs. In one embodiment, the slope of the line represents a total weight that includes the weight of the vehicle and the weight being hauled by the vehicle. The method 900 continues at operation 940 and the weight module 230 determines the weight being hauled by the vehicle by subtracting the weight of the vehicle from the value representing the slope of the line. The method continues at operation 950 and the brake gain value is determined. The method 900 continues at operation 960 and the brake gain signal is sent to the trailer brake control interface, which adjusts operation of the vehicle based on the weight of the trailer by applying brakes to the trailer at operation 970.

FIG. 10 is a flow diagram illustrating one example embodiment of a method for generating calibration polynomials that determine total weight, according to one example embodiment. Operations in the method 1000 may be performed by the trailer brake controller 150, using modules described above with respect to FIGS. 5 and 6. As shown in FIG. 10, the method 1000 includes operations 1010, 1020, 1030, 1040, 1050, 1060, 1070, and 1080. In this example embodiment, the calibration module 270 generates calibration polynomials for each velocity of the vehicle as described in paragraphs 104-109. As one skilled in the art may appreciate, such calibration operations are to be done when the vehicle is not currently hauling a weight.

In one embodiment of the method 1000, the method 1000 begins and at operation 1010, the interface module 220 retrieves a set of vehicle performance parameters as described at least in paragraphs 67-70. In one example, the interface module 220 retrieves a parameter from an interface for the vehicle and from one or more accelerometers included as part of the trailer brake controller 150.

The method 1000 continues at operation 1020 and the performance module 240 determines whether each of a set of vehicle performance parameters are within respective threshold values as described in paragraph 72 through 79. In response to any of the vehicle performance parameters not being within their respective threshold ranges, the method 1000 continues at operation 1010.

In response to each of the vehicle performance parameters being within their respective threshold ranges, the method 1000 continues at operation 1030 and the calibration module 270 calculates a calibration drive force and an engine speed. In one example, the calibration module 270 determines drive force based on a known weight for the vehicle, and determine a drive force by multiplying the weight of the vehicle with the measured acceleration. The method 1000 continues at operation 1040 and the calibration module 270 determines a current velocity for the vehicle and stores the calibration drive force and the engine speed as a data pair in a table for the current velocity.

In one example, the calibration module 270 maintains velocity tables for each integer velocity of the vehicle between 3 and 25 miles per hour (MPH). In this example, in response to a current velocity of the vehicle being 18 MPH, the calibration module 270 stores the data pair in the table for 18 MPH. Over time, as many data pairs are stored, each velocity table includes many data pairs.

The method 1000 continues at operation 1060 and the calibration module 270 performs quadratic regression analysis on each of the velocity tables resulting in a second order polynomial for each velocity of the vehicle. In another example embodiment, the weight module 230 determines a current drive force for the vehicle based on the calibration polynomial for a current velocity of the vehicle.

The method 1000 continues at operation 1070 and the calibration module 270 determines whether an error for each polynomial as compared with the associated set of data points is below a threshold error value. XX in response to any of the polynomials not satisfying the error threshold value, the calibration module 270 continues regression analysis. In response to each of the polynomials satisfying the error threshold value, the method 1000 continues at operation 1080 and the calibration module 270 stores the coefficients for the polynomials.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. 

1. A method comprising: providing predetermined calibration settings relating drive force to motor speed for a vehicle travelling at various speeds; providing accelerometer data to determine vehicle velocity, acceleration, and direction of travel; determining by use of one or more processors, that one or more vehicle performance parameters fall within threshold ranges; determining a total weight of a vehicle and trailer based on the predetermined calibration settings, accelerometer data and the vehicle performance parameters being within threshold ranges; determining a trailer weight by subtracting the weight of the vehicle from the total weight; providing a gain signal for a trailer brake controller; modifying the gain signal based on the trailer weight and the vehicle weight; transmitting the gain signal to the trailer brake controller; applying trailer brakes according to the gain signal.
 2. The method of claim 1, wherein the determining a vehicle weight further comprises: storing, in response to the vehicle performance parameters being within the threshold ranges, a plurality of data pairs, each data pair comprising a longitudinal acceleration and a drive force, the drive force determined according to a calibrated polynomial for a current velocity of the vehicle; determining a slope of a line that linearly approximates the plurality of data pairs, the slope indicating a total weight, the total weight comprising a weight of the vehicle and a trailer weight; determining the trailer weight by subtracting the weight of the vehicle; wherein the determining the slope of the line comprises: setting the initial y intercept of force vs. acceleration to zero; and performing regression analysis on the plurality of data pairs resulting in a first order drive force polynomial, a first order coefficient representing the total weight.
 3. The method of claim 1, wherein the drive force comprises a combined drive force of all motor drive forces, engine drive forces and motive force devices; and wherein providing predetermined calibration settings further consists of relating motor drive force to motor speed for the vehicle traveling at various speeds;
 4. The method of claim 3, wherein the vehicle performance parameters are selected from the group consisting of lateral acceleration, velocity, electric motor speed, electric motor operating in braking mode as a generator, engine speed, longitudinal acceleration, brakes not being applied, and a transmission gear ratio.
 5. The method of claim 1, wherein the gain signal is adjusted based on the ratio of the current trailer weight divided by the original trailer weight.
 6. The method of claim 1, further comprising retrieving one or more of the vehicle performance parameters from a computing device for the vehicle.
 7. The method of claim 3, wherein the combined drive force is determined by determining a polynomial for each integer velocity of the vehicle by performing regression analysis on calibration data pairs for each integer velocity of the vehicle, the calibration data pairs comprising a calibration drive force, an electric motor speed and an engine speed, the calibration drive force determined by multiplying the weight of the vehicle with a longitudinal acceleration of the vehicle when the data pair was recorded.
 8. The method of claim 1, wherein the motor is a motive force device comprising one or more electric motors, internal combustion engines, and external combustion engines.
 9. A system comprising: a vehicle comprising one or more motors; one or more accelerometers that sense acceleration of the system; one or more processors; a drive force module that determines a combined drive force of one or more electric motors, engines and motive force devices; an interface module that retrieves one or more vehicle performance parameters; a performance module that determines whether the vehicle performance parameters fall within respective threshold ranges; a data module that stores, in response to the vehicle performance parameters being within the respective threshold ranges, a plurality of data pairs, each data pair comprising the longitudinal acceleration of the vehicle and a drive force for the vehicle, the drive force determined according to a calibrated polynomial for a current velocity of the vehicle; a weight module that determines the weight being hauled by the vehicle; a brake gain module the determines the brake gain based on current trailer weight and original trailer weight; a brake signal module that transmits a brake gain signal to a brake control module; and the brake control module that applies trailer brakes.
 10. The system of claim 9, further comprising a detection module that records and compares the combined drive force RPM to vehicle speed, and uses this ratio to determine the vehicle's axle ratio and tire size, which is then used to correct the calculated mass.
 11. The system of claim 9, wherein the vehicle performance parameters are selected from the group consisting of lateral acceleration, velocity, engine speed, longitudinal acceleration, brakes application status, and a selected transmission gear.
 12. The system of claim 11, comprising system reset functions: complete system reset upon vehicle being turned off; complete system reset upon vehicle pitch and shaking detection indicating load shift; and complete system reset upon vehicle travelling in reverse direction.
 13. The system of claim 9, further comprising a calibration module that determines a polynomial for each integer velocity of the vehicle by performing regression analysis on calibration data pairs for each integer velocity of the vehicle, the calibration data pairs comprising a calibration drive force and an engine speed, the calibration drive force determined by multiplying the weight of the vehicle with a longitudinal acceleration of the vehicle when the data pair was received, the longitudinal acceleration including the force of gravity, the data module determining the drive force using the polynomial for a current speed of the vehicle.
 14. The system of claim 9, wherein the one or more motors comprising one or more electric motors, internal combustion engines, and external combustion engines.
 15. A computer readable storage medium storing executable instructions thereon, which, when executed by a processor, cause the processor to perform operations including: retrieving one or more performance parameters for a vehicle by one of communicating with diagnostic port for the vehicle and communicating with one or more accelerometers providing accelerometer data; determining a combined drive force; determining filtered data based on the vehicle pitch, roll or both; altering the accelerometer data based on the filtered data; determining that one or more vehicle performance parameters fall within a threshold range; storing, in response to the vehicle parameters being within the respective threshold ranges, a plurality of data pairs, each data pair comprising a longitudinal acceleration and a drive force, the drive force determined according to a calibrated polynomial for a current velocity of the vehicle; determining a slope of a line that linearly approximates the plurality of data pairs, the slope indicating a total weight, the total weight consisting of a weight of the vehicle and a weight being hauled by the vehicle; determining a brake gain signal according to the ratio of the current trailer weight to the original trailer weight; transmitting the brake gain to a trailer brake controller; and applying trailer brakes according to the gain signal.
 16. The computer readable storage medium of claim 15, wherein the operation of determining the slope of the line comprises: setting the initial y intercept of force vs. acceleration to zero; and performing regression analysis on the plurality of data pairs resulting in a first order drive force polynomial, a first order coefficient representing the total weight.
 17. The computer readable storage medium of claim 15, wherein the combined drive force comprises all positive and negative forces from one or more electric motors, engines, and motive force devices.
 18. The computer readable storage medium of claim 17, wherein the vehicle performance parameters are selected from the group consisting of lateral acceleration, velocity, engine speed, longitudinal acceleration, brakes not being applied, electric motor speed, electric motor current, electric motor voltage, and a transmission gear ratio.
 19. The computer readable storage medium of claim 17, wherein the drive force is determined using a polynomial for a current speed of the vehicle, the polynomial generated by performing regression analysis on calibration data pairs for each integer velocity of the vehicle, the calibration data pairs comprising a calibration drive force and an engine speed, the calibration drive force determined by multiplying the weight of the vehicle with a longitudinal acceleration of the vehicle when the data pair was received.
 20. The computer readable storage medium of claim 17, further comprising system reset functions: complete system reset upon vehicle being turned off; complete system reset upon vehicle pitch and shaking detection indicating load shift; and complete system reset upon vehicle travelling in reverse direction. 